-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Removed errors logs from OVA to 4.4 #2019
Removed errors logs from OVA to 4.4 #2019
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Description
After various tests, I was able to detect that the fact that wazuh-manager service was active before the VM was exported generated this error in the logs.
I managed to avoid this error in the logs by adding this service to the provision.sh
Logs example
Tests
https://ci.wazuh.info/view/Packages/job/Packages_Builder_OVA/186/console
OVA: https://packages-dev.wazuh.com/trash/vm/wazuh-4.4.0.ova